use optional dil tensor & move semantics #24
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to optimize the dispatcher for aten ops:
ShadeDataContext
We noticed the creation of dummy DIL tensor in
ShadeDataContext
cost a significant amount of time. So I change thedil_tensor
field to optional.gen_aten_tensor_by
Avoid the unnecessary shallow copy of tensors. Hence we're going to use it this way with a
std::move
.This PR reduce the dispatcher overhead from 90%+ to 20%+. The result was gathered under single thread with jemalloc enabled. The remaining gap is mostly cost by
shallowUpgradeToDPCPPTensor
. That's where we need to optimize in the future.Here's the benchmark script.